chore(changelog): collapse stale Unreleased blocks released in 0.0.10/0.0.11 - #283
Conversation
…nd 0.0.11 Two manual `## [Unreleased]` sections existed in CHANGELOG.md: - One between `[0.0.11]` and `[0.0.10]` whose entries (Homebrew tap publish job, npm publish job) already shipped in 0.0.10 and 0.0.11. Documented in the 0.0.11 Bug Fixes block (#272). - One at the bottom of the file dating to the 0.0.2 era. Every line in that block has been incorporated into a versioned section above (e.g. e2e matrix and baseline/rhythm in 0.0.2, x86_64-apple-darwin drop in 0.0.10, etc.). Both blocks were stale. release-please (release-type: simple) does not consume or maintain `[Unreleased]`; it generates new `## [x.y.z]` sections from conventional commit messages on `main` at release time. Keeping an empty placeholder would invite hand edits, which the file header already forbids. Closes audit finding H18 from the public-surface readiness audit.
|
That confirms the current main is at 0.0.11 — the PR's diff correctly bumps everything to 0.0.12. The output matches the diff already verified. PR #286 —
|
1 participant
Summary
## [Unreleased]block (between[0.0.11]and[0.0.10]) whose entries (Homebrew tap publish job, npm publish job) already shipped in 0.0.10 and 0.0.11. The 0.0.11 Bug Fixes block already documents the wiring (fix(ci): wire homebrew + npm publish jobs into release.yml #272).## [Unreleased]block at the bottom of the file. Every line in it has been incorporated into a versioned section above (e.g. e2e matrix andbaseline/rhythmin 0.0.2,x86_64-apple-darwindrop in 0.0.10, etc.).release-please(release-type: simple) generates## [x.y.z]sections from conventional commits at release time and does not consume[Unreleased]. The CHANGELOG header already forbids hand-editing released sections.Why
From the public-surface readiness audit. Closes finding H18. The duplicate
[Unreleased]block confused the diff and risked release-please mis-handling the next release.Test plan
grep -c '^## \[Unreleased\]' CHANGELOG.mdreturns 0 (zero manual blocks).##headings are released versions in descending order: 0.0.11 → 0.0.2.just validatepasses (fmt, clippy-D warnings, full test suite, determinism check, cargo-deny).